_mmmm_iiii_gggg_rrrr______rrrr_aaaa_nnnn_gggg_eeee______mmmm_iiii_gggg_rrrr_aaaa_tttt_eeee migrates a range of memory to the node where the
_pppp_mmmm_oooo______hhhh_aaaa_nnnn_dddd_llll_eeee has been placed. The _pppp_mmmm_oooo______hhhh_aaaa_nnnn_dddd_llll_eeee can be a placed MLD or an
MLDSET with at least one placed MLD contained within it.
_mmmm_iiii_gggg_rrrr______pppp_oooo_llll_iiii_cccc_yyyy______aaaa_rrrr_gggg_ssss______iiii_nnnn_iiii_tttt fills a migration parameter structure with default
values. This function is applicable to Origin 2000/200 systems, and has
no effect on other Origin systems.
_mmmm_iiii_gggg_rrrr______rrrr_aaaa_nnnn_gggg_eeee______mmmm_iiii_gggg_rrrr_aaaa_tttt_eeee attempts to move all pages that have been faulted in
within the range of _bbbb_aaaa_ssss_eeee______aaaa_dddd_dddd_rrrr plus _llll_eeee_nnnn_gggg_tttt_hhhh. If _bbbb_aaaa_ssss_eeee______aaaa_dddd_dddd_rrrr is not on a page
boundary, the actual start address of the migration is rounded down to
the previous page boundary. If _bbbb_aaaa_ssss_eeee______aaaa_dddd_dddd_rrrr+_llll_eeee_nnnn_gggg_tttt_hhhh is not on a page
boundary, the actual migration length is adjusted by rounding up to end
on the next page boundary. If a page cannot be migrated, it is skipped
and the next page is attempted. If the destination node does not have
enough available free memory to migrate the new pages into, the migration
operation is ended and error is returned (see below). It is usually not
possible to migrate every single page of user memory for a variety of
reasons. A page that is set up for DMA I/O is an example of an un-
migratable page. A page set up for fetchops, a pinned page, a page not
faulted in, and a page that is shared with unrelated processes will not
migrate. In some cases of a physical page shared with several virtual
addresses, it may be migratable if the migrating process can obtain all